The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Determine software fault to be corrected
|
|
Collect and review software fault details from sources Completed |
Evidence:
|
Obtain technical data to assist in identifying problem Completed |
Evidence:
|
Clarify nature of the problem with appropriate person where necessary Completed |
Evidence:
|
Identify and isolate fault
|
|
Review program documentation for specific modules in order to pinpoint problem areas Completed |
Evidence:
|
Review source code for logic errors Completed |
Evidence:
|
2.3 Read manuals, help files and 'read me files' to determine if there is a known fix Completed |
Evidence:
|
Undertake additional testing to identify or duplicate fault Completed |
Evidence:
|
Escalate difficult faults that cannot be identified Completed |
Evidence:
|
Design fix for fault
|
|
Ensure requirements to fix the fault are understood by client Completed |
Evidence:
|
Consider alternative options and choose the most effective solution Completed |
Evidence:
|
Consider the possible impact of the fix on other parts of the system Completed |
Evidence:
|
Document changes according to organisational guidelines Completed |
Evidence:
|
Carry out fix to software
|
|
Identify and obtain access to appropriate software development tools, source code and libraries Completed |
Evidence:
|
Construct appropriate code to correct the fault according to organisational and programming standards Completed |
Evidence:
|
Compile or regenerate code for changed programs and associated modules Completed |
Evidence:
|
Correct and resubmit code until error free Completed |
Evidence:
|
Document changes according to organisational and programming standards Completed |
Evidence:
|
Test fix and associated system areas
|
|
Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere Completed |
Evidence:
|
Request users to perform acceptance testing and record outcomes Completed |
Evidence:
|
Hand over to systems operations area
|
|
Update documentation to reflect all changes made Completed |
Evidence:
|
Confirm acceptance by systems operations and arrange for sign-off according to procedures Completed |
Evidence:
|